Cream of the Crop 11

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 11 / Cream of the Crop 11-2.iso / bbs / metro111.zip / POLICY.DOC < prev

Wrap

Text File | 1995-12-19 | 15KB | 311 lines

─────────────────────────────────────────────────────────────────────────── M E T R O n e t P O L I C Y 1 . 0 4 Revision 12/19/95 Copyright 1995, T.J. McMillen, Jr. ─────────────────────────────────────────────────────────────────────────── - All grammar and spelling mistakes are my fault. 1.0 ── General Rules The official language of METROnet is English. All documents must exist in English, and no other language is permitted to be used, unless otherwise stated by the Zone/Region Coordinator. There will be no slandering/insulting/flaming of any user or any BBS in the public echos under any circumstance. We wish to keep this a realtively peaceful net and hope to make friends, not enemies. There will be no profane language used in the public bases no matter what the case may be. Mild use of expletives will be tolerated to a degree, depending on the descrepency of the moderator of that base. There will be no ANSI/Extended or High ASCII/RIP or any other graphic/code placed in any echo of METROnet. Also, there will be no XX or UU Encoding or encrypting of any kind in the net and it will not be tolerated in any public message base. When posting, PLEASE keep to the topic of the base posting the message in. Such as, if post something for sale, don't post it in the Renegade/BBS Help Base, post it in the FOR SALE base. That is why there are different bases. If we wanted things to be cluttered we would have only one base. We ask that METROnet SysOps move off-subject posts to the appropriate base. The Moderator of an echo has EVERY right to tell you what you can and CANNOT do in that echo, as long as they are keeping within the METROnet Guidlines. Remember, what they say goes, and the moderator must be treated with respect. Sigs or Signatures, will not be allowed to exceed 3 lines in order to keep packet size down. A signature can only be placed on a message with atleast 3 lines of written words, not quoted, text. ─────────────────────────────────────────────────────────────────────────── 2.0 ── Echos - Rules The METSYSOP & METUSER echos are ONLY allowed to be viewed and posted upon by the person/party whose name appears in the METROnet Nodelist (METLIST). Failure to do so, by leaking information, can result in a suspension, or a loss in the node address. 2.1 ── Echos - Adding Any echo can be added to the backbone feed as long as at least one (1) METROnet SysOp and at least three (3) other METROnet SysOps are willing to carry the echo on their BBS (does not apply to mail only Bulletin Boards). Echo requests are to be submitted to the Zone/Regional Coordinator for incorporation into the net. Newly added echos will be given one (1) month of testing. Within that time if insufficient message traffic is created, the echo will be removed from METROnet. Sufficient traffic is a topic decided by the Zone/Regional Coordinator. There will be a maximum of three (3) new bases per a 6 month period and bases of similar subjects will only be given one (1) chance per 6 month period. If interested in adding an echo, post all information such as, base name, and a brief description of the base and nodes wanting the echo will vote on it. Remember, a total of 4 nodes MUST request the echo for it to be added. The Zone Coordinator is excluded from all voting, unless the message echo(s) in question were suggested by him/her. 2.2 ── Echos - File Bone The Nodelist and Application FileEcho is to be only MetroNet Applications and Nodelists. No other nets or person's besides the Zone Coordinator can post in this base. Other FileEchos can send AND receive files. More rules will be placed if needed upon the FileEchos. 2.3 ── Echos - Real Names/Handles All echos are allowed to use handles EXCEPT the METROnet "For Sale" echo. This is because of buying and selling of goods is an important subject and buyers/sellers must reveal their identity. 2.4 ── Echos - No Alteration of Mail You may not modify, other than as required for routing or other technical purposes, any message, netmail or echomail, passing through the system from one METROnet node to another. If you are offended by the content of a message, then contact your Zone/Region Coordinator for information on what to do. 2.5 ── Echos - Black Listings Echo The METUSER Conference (The Black List Echo) will have a strict set of guidelines to follow; as in: List User handle *AND* real name is possible. (If not possible, SysOp of offending BBS MUST ONLY IF NECESSARY post the offender(s) real name.) List cause / probable cause / problem. Post message or E-Mail calling / warning for such an action from the offender(s). No idle Chit-Chat, just post to worn, not to bash! 2.6 ── Echos - Gating There will be no gating of any METROnet echos, unless absolutly wanted by the entire net. 2.7 ── Echos - Tag/Tear Lines All nodes carrying METROnet must have a tag/tear line at the close of each message posted from their BBS. Tear/Tag lines may have any saying you wish (within limits), but it would also be a good idea to include the area code and phone number of your BBS somewhere for the people to see. ─────────────────────────────────────────────────────────────────────────── 3.0 ── Regions / Hosts / Hubs All METROnet Nodes will be in the format of 25:(AREACODE)/XXXX with the exception of the 412 Are Code which is in the format of (25:25/XXXX). All regions will be the main pickup point of mail transfers for their downlinks. All hosts will destribute all mail to their hubs/downlinks. All hubs will destribute mail for all nodes that is supports. All Region/Host/Hub Coords. MUST have the latest METROnet Nodelist up for FREQ and must destribute it whenever they receive a new nodelist. 3.1 ── Regions / Hosts / Hubs - Tradition A coordinator is not bound by the practices of predecessor or peers beyond the scope of this policy. In addition, a new coordinator has the right to review any decision made by predecessors for compliance with Policy, and take whatever actions may be necessary to rectify any situations not in compliance. ─────────────────────────────────────────────────────────────────────────── 4.0 ── The Nodelist The METROnet Nodelist is destributed each and every Friday by the Zone Coordinator (25:25/0) to all Regions/Hosts and Hubs. It is each Region/Host/Hub responiblity to distribute the nodelist to each of their nodes. Any additions to the METROnet Nodelist should be sent to 25:25/0 on or before Thursday of that week. To reduce complication, the METROnet Nodelist is assigned a day of (.000) and will remain so until it is necessary to make any changes in the current format. 4.1 ── The Nodelist - Changes There will ONLY be changes made to the METROnet Nodelist by the such adminstrative nodes as Zone/Region/Host/Hub(s). Any other changes in the metlist is *NOT* supported by the Zone Coordinator and such violates this policy ad copyright laws based upon this. ─────────────────────────────────────────────────────────────────────────── 5.0 ── Pirating/Freaking/Hacking There will be no such talk about hacking, freaking or pirating of software, anywhere on METROnet. If such talk is dicussed, you will receive a warning and the next offence you will be black listed. ─────────────────────────────────────────────────────────────────────────── 6.0 ── User/Node Status If your node will be down for an extended period (more than a day or two) inform your coordinator as soon as possible. It is not your coordinator's responsibility to chase you down for a status report, and if your system stops accepting mail it will be removed from the nodelist. Never put an answering machine or any other device which answers the phone on your phone line while you are down. If you do, calling systems will get the machine repeatedly, racking up large phone bills, which is very annoying. In short, the only thing which should ever answer the telephone during periods when the nodelist indicates that your node will accept mail is FidoNet- compatible software which accepts mail. If you will be leaving your system unattended for an extended period of time(such as while you are on vacation), you should notify your coordinator. Systems have a tendency to "crash" now and then, so you will probably want your coordinator to know that it is a temporary condition if it happens while you are away. 6.1 ── User/Node Status - Excommunication A system which has been dropped from the network is said to be excommunicated (i.e. denied communication). If you find that you have been excommunicated without warning, your coordinator was unable to contact you. You should rectify the problem and contact your coordinator. It is considered annoying behavior to assist a system which was excommunicircumventing that removal from the nodelist. For example, if you decide to provide an echomail feed to your friend who has been excommunicated, it is likely that your listing will also be removed. 6.2 ── User/Node Status - Responsiblity The sysop listed in the nodelist entry is responsible for all traffic entering METROnet via that system. This includes (but is not limited to) traffic entered by users, points, and any other networks for which the system might act as a gateway. If a sysop allows "outside" messages to enter METROnet via the system, the gateway system must be clearly identified by a METROnet node number as the point of origin of that message, and it must act as a gateway in the reverse direction. Should such traffic result in a violation of Policy, the sysop must rectify the situation. 6.3 ── User/Node Status - Behavior It is difficult to define this term, as it is based upon the judgement of the coordinator structure. Generally speaking, annoying behavior irritates, bothers, or causes harm to some other person. It is not necessary to break a law to be annoying. There is a distinction between excessively annoying behavior and (simply) annoying behavior. For example, there is a learning curve that each new sysop must climb, both in the technical issues of how to set up the software and the social issues of how to interact with METROnet. It is a rare sysop who, at some point in this journey, does not manage to annoy others. Only when such behavior persists, after being pointed out to the sysop, does it becomes excessively annoying. This does not imply that it is not possible to be excessively annoying without repetition (for example, deliberate falsification of mail would likely be excessively annoying on the very first try), but simply illustrates that a certain amount of tolerance is extended. 6.4 ── User/Node Status - Moderators The Moderator of an echo will be in full control of that echo they moderate. Incase of a "bogie" moderator, the Zone/Region Coordinator will take approite action(s). ─────────────────────────────────────────────────────────────────────────── 7.0 ── Inter-BBS Games METROnet has two Inter-BBS Games, BRE & FE. These games are running at the same time and all resets will be on a quarterly basis. (3 Month Games) BRE & FE Schedule Game 1 - January 1st - March 31st Game 2 - April 1st - June 30th Game 3 - July 1st - September 30th Game 4 - October 1st - December 31st Information on joining either game is always included in the latest METROnet Application Pack or by contacting the Zone 25 Coordinator at 25:25/0 and requesting info on the Inter-BBS Games. You do not have to join both games, you can join either one or both. (Remember, if you send any requests or questions to 25:25/0, you must poll back within 24 - 48 hours to get your reply.) Incase of an updated version of the game that comes out and requires a reset, we will upgrade a few days before the next reset is made league-wide. If the version being used currently is very unstable we will either upgrade or downgrade to a more stable version. We'll run that version until a new version is released or the date on a reset approaches.